Agilent I/O Libraries for Windows
Revision History

Click on the links below for information on the following subjects:

• General Information ...
• Installation and Configuration Information ...
• Application Notes ...
• Troubleshooting Guide...
• Revision History:
  • J.02.00 (November 2000)
  • J.01.02 (October 2000 - Web only)
  • J.01.01 (August 2000)
  • J.01.00 (June 2000)
  • H.01.03 (February 2000)
  • H.01.02 (December 1999)
  • H.01.00 (June 1999)
  • G.02.02 (January 1999)
  • G.02.01 (August 1998)
  • G.02.00 (July 1998)
  • G.01.01 (April 1998)
  • G.01.00 (March 1998
  • F.01.02 (April 1997)
  • F.01.01 (December 1996)
  • F.01.00 (October 1996)

J.02.00 (November 2000)

New Features

• Support for Windows Me has been added.
  • Note that due to Windows configuration manager changes made by Microsoft, the 82341C ISA GPIB card and the E2075 ISA GPIO card are not supported on Windows Me.
• Two new request codes are available for the iserialctrl() function in SICL.
  • I_SERIAL_IN_DISCARD - The following actions will occur:
    • The data in the serial input buffer will be discarded
    • Any error conditions will be reset.
  • I_SERIAL_OUT_DISCARD - The following actions will occur:
    • Any pending writes will be aborted.
    • The data in the serial output buffer will be discarded
    • Any error conditions will be reset.
• Three new request codes are available for the iserialstat() and iserialctrl() function in SICL.
  • I_SERIAL_XON_CHAR
    • Get / Change the character used for stopping transmission when using software handshaking.  The default is 0x11.
  • I_SERIAL_XOFF_CHAR
    • Get / Change the character used for re-starting transmission when using software handshaking.  The default is 0x13.
  • I_SERIAL_REPLACE_CHAR
    • Get / Change the character used to represent a 'bad' received character (e.g. parity error).  The default is 0xff.
• Since version J.01.00, the IO Libraries installation program will detect the presence of National Instruments VISA and will default to installing only SICL in this case so we will not overwrite NI-VISA.  You can force Agilent VISA to overwrite NI-VISA by selecting the Full SICL and Agilent VISA Installation menu choice when installing the IO Libraries.

Fixes

• In the viFlush() VISA function, it is now possible to discard the ASRL in and out buffers separately.
  •  VI_ASRL_IN_BUF_DISCARD and VI_ASRL_OUT_BUF_DISCARD no longer need to always be set together.
  • If only one is set, VI_ERROR_INV_MASK no longer returned.
• The following attributes are  now supported with the VISA functions viGetAttribute() and viSetAttribute() for ASRL sessions:
  • VI_ATTR_ASRL_XON_CHAR
  • VI_ATTR_ASRL_XOFF_CHAR
  • VI_ATTR_ASRL_REPLACE_CHAR
• If there are no IRQ's  available for an auto-configured 82341C ISA GPIB card, a dialog box is presented when the IO Configuration program is run.  Previously no indication was given but the card would not work.
• SICL LAN Client with the host specified by IP address, no longer requires an entry in the HOSTS table.
• The IO Configuration program no longer displays configuration warnings when uninstalling the IO Libraries.
• The IO Libraries setup program no longer fails if msvcrt.dll is not installed on the system.
• Some bad shortcuts in the Agilent IO Libraries and VXIPNP program folders have been fixed.
• Some defects in the E8491 VXI Resource Manager program have been fixed.
• The 'actualcnt' parameter returned by iwrite() in a commander session to a GPIB device now returns the correct value.  It used to return a large apparently random number if a timeout occured before any bytes were sent. This problem also affected viWrite().

Issues

• 82341C GPIB cards and E2075A GPIO cards are not supported on Windows Me.
  • Due to Windows configuration manager changes made by Microsoft, these ISA cards are very difficult to configure and can cause the computer to hang during the configuration process.  Refer to the troubleshooting page for more information.
• The 82341D GPIB card is not supported on Windows 2000.
  •   Note, however, that the 82341C card is supported.
• The Adaptec PCI to 1394 card which originally shipped with the E8491 VXI to 1394 interface is not supported on Windows 2000.
  • This original card was not OHCI compliant and only OHCI 1394 cards are supported on Windows 2000.
  • The E8491 is now shipping with an OHCI compliant card which is supported on Windows 2000.
• Beginning with the J.01.00 revision, the default paths for IO Libraries and VISA have changed to:
  • '\Program Files\Agilent\IO Libraries' for SICL
  • '\Program Files\VISA' for VISA
  • If you are installing over a previous version of the IO Libraries, the directories will not be changed.
• We recommend downloading a Windows 2000 hotfix from Microsoft to resolve two known problems which affect the E8491. 
  • Block write and I-SCPI performance on the E8491 on Windows 2000 are significantly reduced due to the workaround for a memory leak in the 1394 driver.
  • Performance problems and missed interrupts on Windows 2000 are possible due to a busy-acknowledge defect in the 1394 driver.  This is known to affect some E8491 firmware downloads and some I-SCPI and VXIplug&play drivers.
  • Microsoft has implemented a hotfix which solves both of these problems.  Go to http://www.microsoft.com and search for Q262814 to find the Knowledge Base article with information on obtaining the hotfix .  If you have difficulty, contact Agilent Support for more information.
  • The hotfix must be obtained from Microsoft.  Microsoft does not allow Agilent to distribute Windows 2000 hotfixes. 
  • Microsoft has stated that this fix will be included in the Windows 2000 Service Pack 2 when it becomes available.
  • The E8491 driver will sense the presence of the hotfix or Service Pack 2 and automatically switch to a higher performance mode if either is installed.
• We recommend downloading a Windows 98/Me hotfix from Microsoft to resolve a known  IEEE 1394 problem which affects the E8491.
  • Performance problems and missed interrupts on Windows 98 and Windows Me are possible due to a busy-acknowledge defect in the 1394 driver.  This is known to affect some E8491 firmware downloads and some I-SCPI and VXIplug&play drivers.
  • Microsoft has implemented a hotfix which solves this problem.  You can find out more about this hotfix by going to http://www.microsoft.com and searching for Q252185 to find the Knowledge Base information on obtaining the hotfix .  If you have difficulty, contact Agilent Support for more information.
  • The hotfix must be obtained from Microsoft.  Microsoft does not allow Agilent to distribute Windows hotfixes.
• There is a memory leak in Windows 98 which may affect the IO Libraries operation.
  • We have observed a 4 Kb memory leak each time any program that dynamically links the Microsoft msvcrt.dll (even a program that does not do IO) is run and then exits on Windows 98.  This DLL is the C runtime library supplied with Microsoft Visual Studio and it is used by many products.
  • The IO Libraries dynamically link to msvcrt.dll so any program using SICL and / or Agilent VISA will exhibit this problem.
  • If your application involves starting and stopping programs many times, you will eventually run out of memory.  Windows 98 will gradually become sluggish and eventually quit.  The only solution to this problem is to reboot.
  • We are reporting this defect to Microsoft but there is no resolution yet available.
  • Note: If in Microsoft Visual Studio, you choose 'Multithreaded DLL' in the 'Use run-time library:' box on the C/C++ Code Generation tab, your application will dynamically load msvcrt.dll.
• When three or more E8491's are connected to a single IEEE 1394 interface card, certain topologies may not work.
  •  In certain topologies the E8491 hardware is not properly identified on the 1394 bus.  This will result in inconsistent behavior when the VXI resource manager tries to configure instruments in the VXI card cages.  
  • Behavior may include timeout errors while attempting to communicate with a particular instrument, and / or instruments appearing in cages where they are not actually located .
  • Try reversing the cable connections to the ports on the  host interface card    In general, cable connections with longer chains of E8491's should be on lower host ports.
• Don't re-run setup too quickly.
  • After the IO Libraries Setup program exits, it takes several seconds to clean up and unload itself from memory.  If Setup is re-run before this process is complete, you may see an error message or find that the re-installation does not behave as expected.
  • Be sure to wait until the 'InstallShield Wizard' box on the Windows task bar has disappeared before attempting to re-run the IO Libraries Setup.
• Installing on dual boot systems can cause problems.
  • Installing the IO Libraries on dual boot systems that share a common 'Program Files' directory between two operating systems is not recommended and may cause problems.
  • If the IO Libraries are installed in the same directory for both operating systems (e.g. 'Program Files\Agilent\IO Libraries'), files for one OS may overwrite files for the other OS.
  • InstallShield uses a directory under 'Program Files' to log the name and location of files for later un-installation as well as the components that are currently installed.  Uninstalling or modifying an installation on one OS may affect the files for the other OS rather that the currently booted OS, even if these files are installed in different directories.
• The syntax for specifying a parameter with the self-installing .exe file 'iolibs.exe' is different from specifying a parameter with Setup.exe on the CD.
  • To specify options to Setup, invoke Setup from a command prompt and separate the options with spaces:
        e.g. 'setup auto novisa'
  • When installing from the self-installing .exe file, you must include a '-a' option as the first option:
        e.g. 'iolibs -a auto novisa'
• Setup from the self-installing .exe file may prompt for bogus disk.
  • If you install the IO Libraries from the self-installing .exe file using a parameter (e.g. 'iolibs -a auto'), you may be prompted to insert a non-existent disk.
  • You may continue the installation by specifying the last available disk in the set.
• After installation on Windows 95 and Windows 98, Windows may fail to boot.
  • When adding paths to the PATH statement in Autoexec.bat, InstallShield does not recognize '@PATH' as a path statement.  It will create a second 'SET PATH' statement.  If there is a second PATH statement, it will replace the existing Windows PATH and end up removing the Windows directories from the PATH.
  • If Windows fails to boot with a message 'Cannot find WIN.COM, unable to continue loading Windows', you will need to edit the additional PATH statement in Autoexec.bat so the Windows directories are again included in the PATH.  
    • From the DOS prompt type 'c:\windows\command\edit c:\autoexec.bat'. (Substitute the actual paths if you have a non-standard installation.)
    • Find the last 'SET PATH=...' statement and insert '%path%;' immediately after the equals sign.  (e.g. 'SET PATH=%path%;...' and don't forget the semi-colon separator.)
    • Save the modified file and reboot.  Windows should now boot normally.
• If the E8491 is very busy and an IEEE 1394 bus reset occurs, it may become unresponsive and require a reset of the E8491 and/or a reboot of the computer. 
  • This problem can occur when another 1394 device is added or removed while the E8491 is busy.

Known Defects

• On E623x Embedded Pentium Controllers, the SICL directory name must be in standard DOS 8.3 form.  If a long directory name or a name with spaces is used, the VXI driver will not be able to locate a required DLL.
• Calling iblockmovex() on an Agilent E8491 interface to copy data from VXI to host computer memory can cause NT to crash if not enough memory has been allocated to hold all of the data.
• Calling viClose() on the last viOpenDefaultRM() session causes a small memory leak. If you need to call viOpenDefaultRM() and viClose() in a loop or if you are opening and closing a lot of VXI Plug&Play drivers, you should also call viOpenDefaultRM() once in the beginning of your program to ensure you are not closing the last viOpenDefaultRM() in a loop.
• Win95 RS-232/SICL does not give error indication on buffer overrun.
• On Win95 and Win98  if VISA runs out of resources (too many open sessions, for example), it will leave 16 bit DLL's loaded in memory after the program exits. The workaround is to logoff and the logon again or to reboot windows. A user can also use tools such as wps.exe to manually unload the 16 bit DLL's.
• VISA viLock()/viUnlock() does not work on devices accessed via LAN.
• viOpenDefaultRM fails when using GPIB-VXI over an Agilent 37204 GPIB extender. The GPIB extender handshakes all GPIB addresses even if there are no devices present. This confuses the algorithm used by viOpenDefaultRM to identify the devices present. The workaround is to manually configure all devices that are physically connected to the affected interface. This is done by running the I/O configuration utility, selecting the affected interface and navigating to the 'Edit Visa Config' dialog box. From this dialog box, you can disable 'identify devices at run-time' and manually add the devices that are connected to the interface.
• Simultaneous interrupts on different VXI interrupt lines on an Agilent E623x can cause interrupts to cease working until power is cycled or the computer is reset (not just re-booted). The workaround is to have all devices interrupt on the same VXI interrupt line.
• viWrite() and iwrite() to a serial device can fail when the serial input buffer has overflowed. The workaround is to call viFlush() or iflush() on the receive buffer immediately before doing the viWrite() or iwrite().
• Agilent 8234x cards do not work on multi-processor Windows NT systems.  The only workaround currently available is to boot NT in single processor mode.
• VISA Config "Auto-add devices" fails with error on Agilent E623x/Win 95. The workaround is to add devices manually.
• EPC-7/8/VXLink/Agilent E823x do not report bus errors on VXI transfers.  The value returned when a bus error occurs is all 1's.
• On the Agilent E623x Embedded Pentium Controller running WinNT, when using iblockmovex (SICL) or viMoveIn/viMoveOut (VISA) to move very large blocks, if a page fault occurs in the TULIP driver, NT will blue screen with an IRQL_NOT_LESS_OR_EQUAL error in BusMgr.sys.   Apparently BusMgr.sys cannot handle a page fault in the local memory buffer. The workaround is to lock the local buffer in memory before beginning the transfer. This can be done using the Win32 API Calls: SetProcessWorkingSetSize(), VirtualLock() and VirtualUnlock(). Note locking large buffers in memory can have a negative impact on overall system performance.
• On Agilent 623x platforms running Windows NT, sending ivxiws() to a device that you expect a response from can hang at NT Kernel level if the device does not respond. Once this happens, you need to reboot NT to recover. The simple workaround is to always set a reasonable timeout on the device session before issuing the ivxiws() call.
• On Agilent E623x platforms, SICL iopen() of a locked device will hang waiting for the lock. The workaround is do all iopen()'s before locking any devices. Note that you cannot set a timeout for the iopen() since the timeout must be set on an already open SICL session.
• On Agilent E623x platforms, SICL ilock() does not work across processes. Even if a device is locked in one process, it can still be accessed in another process.
• A VISA address string containing a leading 0, e.g. GPIB0::08::INSTR does not work. Leading 0's must be removed in order for VISA to find the desired device, e.g. GPIB0::8::INSTR.

J.01.02 (October 2000 - Web only)

New Features

• None

Fixes

• An 82341 GPIB card configuration problem on Windows 2000, which could cause a blue-screen at boot up, has been solved. [J.01.01.01 (September 2000)]
• A problem with large block transfers using on 1394 cardbus cards which use the NEC 1394 chipset has been solved. [(J.01.02.00) October 2000]

J.01.01 (August 2000)

New Features

• Windows 2000 support for the following interfaces has been added:
  • E8491 IEEE 1394 to VXI interface
  • 82341C and 82350 GPIB Cards
  • RS-232 Serial Ports
  • E2050 LAN to GPIB
  • E2070 GPIO Cards
  • SICL and VISA LAN Client
  • SICL LAN Server
• E8491 Support on Windows 98 has been added.

Fixes

• A number of E8491 problems on Windows 2000 and Windows 98 have been fixed.
• Rebranding of the product from Hewlett-Packard to Agilent Technologies has been completed.
• An 82341 GPIB card configuration problem on Windows 2000, which could cause a blue-screen at boot up, has been solved. [J.01.01.01 (September 2000)]

J.01.00 (June 2000)

New Features

• Windows 2000 support for the following interfaces has been added:
  • E8491 IEEE 1394 to VXI interface
  • 82341C and 82350 GPIB Cards
  • RS-232 Serial Ports
  • E2050 LAN to GPIB
  • E2070 GPIO Cards
  • SICL and VISA LAN Client
  • SICL LAN Server
• E8491 Support on Windows 98 has been added.

Fixes

• A problem with recognizing the 82350 GPIB card on newer computers has been solved.
• A problem with dynamically loading the I/O Libraries in multi-threaded applications has been fixed.  Thread local storage is now properly initialized even on threads created before the I/O Libraries were loaded.
• A problem with changing the serial input and output buffer sizes in VISA using viSetBuf() has been fixed.
• A GPIB timing problem which on rare occasions causes a timeout error has been fixed.
• Several E8491 defects have been fixed

H.01.03 (February 2000)

Enhancements / Fixes / Changes

• This release was distributed only with the E9850A and E8491 products.
• Support for the E9850A VXI Embedded Pentium Controller was added.
• An E8491B firmware defect were fixed.
• A problem with dynamically loading the I/O Libraries in multi-threaded applications has been fixed.  Thread local storage is now properly initialized even on threads created before the I/O Libraries were loaded.
• A problem with changing the serial input and output buffer sizes in VISA using viSetBuf() has been fixed.
• A GPIB timing problem which on rare occasions causes a timeout error has been fixed.
• A number of re-branding changes from Hewlett-Packard to Agilent Technologies were made.

H.01.02 (December 1999)

Enhancements / Fixes / Changes

• A number of E8491A/B firmware and driver defects were fixed.
• A number of 82350 Windows NT driver defects were fixed.
• A %E conversion error was fixed:   For example:  executing viPrintf( vi, "%E\n", -3.0e-3 ); would send "-3.000001E-03" where "-3.000000E-03" is expected. This is now fixed.

H.01.00 (June 1999)

Enhancements / Fixes / Changes

• The I/O Libraries Readme information has been changed from a text file to several linked HTML files.
• Agilent E8491B IEEE 1394 to VXI Interface has been added.  This interface provides faster VXI transfers than the E8491A.
• This revision no longer supports:
  • Windows 3.1 and Windows NT 3.51.
  • 16-bit applications on Windows 95 and Windows 98.
  • Old ISCPI  (ISCPI drivers that use SICL rather than VISA)
• A problem with ANSI to UNICODE conversion errors in Visual Basic when a device times out has been fixed.
• A problem on Windows NT where the VXI ISCPI files were being installed in the wrong directory has been fixed.
• On Windows 95 and Windows 98, interrupt and SRQ handlers now execute in the context of the correct thread.  This fixes potential GPF's in certain situations.

G.02.02 (January 1999)

Enhancements / Fixes

• An I/O Libraries control  icon was added to the system tray. In G.02.01, this icon was only present if you installed the Agilent E8491. It is now installed for all interfaces. Clicking this icon gives you convenient access to:
  • VXI Resource Manager (Agilent E8491)
  • Visa Assistant
  • I/O Config
  • Documentation (manuals and help files)
  • Visa Message logging and viewing (for debug purposes)
• Adaptec drivers for Agilent E8491 can now be uninstalled.
• The way VISA scans for devices has been changed:
  • ViOpen will now find devices that were not present when viOpenDefaultRM() was first run.
  • VISA no longer scans for devices when you call viOpenDefaultRM().
  • VISA now scans for new devices each time you call viFindRsrc().
• You can override the automatic scanning for interface cards when you run I/O Config. This will prevent problems on some PC's which malfunction when certain addresses are touched during the configuration process. See the file <SICLbase>\intfcfg\intfcfg.txt for details. The interfaces which can be manually configured are:
  • COM ports
  • Agilent 82340
  • Agilent 82341A/B/C/D
  • Agilent E2075
• I/O Libraries setup has been improved:
  • You won't be prompted to reboot unless it is necessary.
  • By default, interfaces will be configured automatically.
  • The Uninstall program does a better job of freeing system resources used by non-plug&play I/O cards.
• When installing the I/O Libraries, if a file exists that has the same name as one of the I/O Libraries directories, a bogus error message was generated. First a message box appears prompting you to insert the next disk. When you click OK to that, another message box appears: Unable to create a directory under D:\WINNT\System32. Please check write access to this directory. Setup then quit.  A more descriptive error message is now generated if this should occur.
• For a GPIO card, I/O Config had reversed the definitions of the DIN polarity and DOUT polarity. This has now been fixed.

G.02.01 (August 1998)

Enhancements / Fixes

• A problem with using GPIB cards on fast PC's was fixed.

G.02.00 (July 1998)

Enhancements / Fixes

• Support was added for the Agilent E8491 IEEE 1394 to VXI interface.

G.01.01 (April 1998)

Enhancements / Fixes

• A problem with GPIB-VXI accessing non-A16 memory was fixed.
• A problem on Win95 where I/O Config would occasionally find a bogus Agilent 82350A card when none were installed was corrected.
• On WinNT, device drivers are no longer loaded for I/O cards that are not configured. This eliminates a potential blue-screen problem on some computers.

G.01.00 (March 1998)

Enhancements / Fixes

• Support for the Agilent 82350A PCI GPIB card was added.
• VISA Spec Revision 1.1 is supported beginning in release G.01.00.  This adds:
  • MEMACC resource: Allows access to the entire VXI A16, A24 and A32 Memory Space.
  • viMove(): Moves data between memory and VXI in either direction. Access size (VI_WIDTH_8, VI_WIDTH_16 and VI_WIDTH_32) is passed as a parameter.
  • %b and %y format specifiers have been added to viPrintf and viScanf to allow the reading and writing of IEEE 488.2 Arbitrary Block Program Data and raw binary data.
  • VI_NULL can now be used in place of an OUT parameter in several if the value of the OUT parameter is not needed by the programmer.
  • The VISA 1.1 specification provides for but does not require VME card support. VME cards will have logical addresses between 256 and 511. Their configuration in the system is vendor specific. Agilent has not implemented VISA support for VME cards at this time.
• The VISA and SICL manuals are included in electronic form on the Agilent I/O Libraries CD-ROM beginning with release G.01.00.
• Two threads in the same process attempting to close the same VISA object at the same time will no longer cause a GPF.
• viClose() disables all events and allows time for all interrupt threads to complete before the session object is destroyed.
• viMoveIn() and viMoveOut() now work correctly with Agilent Command Modules.
• On Windows 95, I/O Config can now configure up to 256 COM ports. This is done by editing the \intfcfg\intfcfg.ini file. This file is installed when the Agilent I/O Libraries are set up. Refer to the documentation in that file for details on how to configure additional COM ports.
• viWrite now functions correctly when buffer to be written is in read-only memory.
• The missing VISA entry points have been added to the Borland version of the VISA32.LIB import library.
• GPIB-VXI DLL now correctly computes the A24 membase on all cards.
• viOut32() no longer returns a bogus error code of VI_ERROR_NSUP_WIDTH.
• GPIB-VXI viMoveIn16 now handles FIFO moves correctly.
• I_GPIO constants have been added to the sicl4.bas file.
• Using GPIB-VXI on an Agilent command module, viIn32() no longer reports VI_ERROR_TMO.
• Changing length of VISA name (i.e. gpib0 to gpib11) now works.
• A thread-safe defect in GPIB I/O on Windows NT has been corrected.
• Agilent I/O Libraries setup program on Windows NT no longer fails with a very long system 'PATH' environment string.
• iwaithdlr() now works correctly on 16 bit Windows 95 regardless of the setting of the Sicl Yield flag.
• iopen(NULL) no longer causes an occasional GPF in 16 bit Windows 95.

F.01.02 (April 1997)

Enhancements / Fixes

• Windows 3.1 SICL / VTL 3.0 bits have been added to the CD-ROM.
• An 'Options' menu was added to I/O Configuration program. This menu allows user changes to VISA logging mode and SICL Yield mode:
  • VISA logging is now 'off' by default.
  • SICL Yield mode is now 'false' by default.
• On Windows NT, the LAN Server is not auto-started when it is configured. Now, when the LAN Server is configured on Windows NT, a dialog box informs the user to either start it manually or add a shortcut to it in the StartUp folder.
• A configuration problem on Windows 95 Service Release 2 has been fixed.
• A memory leak on Windows NT VXI interface has been fixed.
• An intermittent RS-232 I/O error has been fixed.
• A GPIB-VXI problem with A24 memory access on some VXI cards when using an Agilent Command Module has been fixed.
• I/O Libraries can now be successfully installed on Win95 in a path which contains long file names.
• Folder shortcuts to I/O Library programs now work correctly when the I/O Libraries are installed in a path whose name contains spaces.
• The I/O Libraries setup program no longer fails when attempting to install on a disk with more than 2Gb of free space.
• I/O Libraries can now be use on WinNT when not an administrator.
• Tab-stops in scroll boxes in the I/O Config program have been fixed so they can be edited from the keyboard as well as with the mouse.
• A potential data corruption problem on Agilent 82341 card when used on some PC's which don't fully meet the ISA backplane spec has been fixed.
• VISA resource strings are no longer case sensitive. Previously they were required to be uppercase.
• On Windows NT, VXI interrupts are no longer lost if they occur too close together in time.
• A number of user interface improvements have been made to the Visa Assistant program which ships with the I/O Libraries.

F.01.01 (December 1996)

Enhancements / Fixes

• Simultaneous VXI TTL triggers no longer cause Windows NT to hang and require a reboot, when running on an Agilent E6233A computer.
• The GPIB-VXI support files are now installed on non-VXI platforms. Note: A setup program for these files has also been added to the November 1996 release of the Agilent Plug&Play Driver CD.

F.01.00 (October 1996)

Enhancements / Fixes

• Up to 256 RS-232 ports can now be configured (limit used to be 9).
• The I/O Config program now runs on non-USA versions of Windows NT.
• ipeek and ipoke are now functions rather than macros. The compiler optimizer would, under certain conditions, generate wrong size VXI backplane accesses when macros were used.
• A potential hang problem in Win32 with iserialctrl(I_SERIAL_RESET) has been fixed.
• Many SICL for Visual BASIC 4.0 improvements, particularly for binary read/write.
• Visual Basic iwrite() now correctly sets the 'actual' parameter return variable under all conditions.
• isetbuf() is now supported in Visual Basic 4.0.
• For 16 bit VISA/VTL in Windows 95, vxipnp\win\bin is now added to the PATH and the VPNPPATH environment variable is set.
• A problem in WinNT 4.0 in which viOpenDefaultRM() caused an exception is now fixed.

⌐ Copyright 1995-2000 Agilent Technologies.  All Rights Reserved.
⌐ Copyright 1984, 1985, 1986, 1987, 1988 Sun Microsystems, Inc.
⌐ Copyright 1996 Microsoft Corporation. All Rights Reserved.